home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: big endian, little endian
- Date: 17 Apr 1996 09:11:57 -0700
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4l358dINN9n4@keats.ugrad.cs.ubc.ca>
- References: <4ku9dm$t1t@news.ycc.yale.edu> <3172C1E9.3E95@willows.com> <829730230snz@willen.demon.co.uk>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <829730230snz@willen.demon.co.uk>,
- Adrian Parker <adrian@willen.demon.co.uk> wrote:
- >In article <3172C1E9.3E95@willows.com>
- > tarang@willows.com "Tarang Deshpande" writes:
- >
- >> it has to
- >> do with how integers are represented in memory on different platforms.
- >
- >Ah, I see.. so is there a proper name for the problem of different
- >sizes of ints as well as the different storage methods ?
-
- Yes: ``word size'' and ``byte order'', respectively.
-
- Add to that ``alignment'', since machines may differ in what kinds of words you
- can load and store to addresses that are not divisible by 2, 4 or 8, etc.
-
- And of course, there is ``representation''. How does the machine interpret the
- bits of the integer or floating point number for the purpose of doing
- arithmetic with it? How are bit patterns assigned values?
- --
- I'm not really a jerk, but I play one on Usenet.
-